-- card: 4404 from stack: in
-- bmap block id: 0
-- flags: 0000
-- background id: 2808
-- name: 


-- part contents for background part 5
----- text -----
     Next, the button script calls my ResCopy XCMD to copy each resource that I want the user to have. Here is where the XCMD takes over...

     ResCopy opens the source file by it's pathname. If there's no problem opening it, it assumes that everything is fine.

     ResCopy then tries to open the destination file by it's pathname. If there's an error, it assumes it's because the file doesn't have a resource fork. Stacks aren't created with resource forks. If this happens, then ResCopy creates a resource fork in the stack. In fact, it's possible to use ResCopy in this way to create a new resource file, by not giving it the name of an existing file.

     Now, at this point, both files are open, and ready for copying.

-- part contents for background part 7
----- text -----
7